Repository navigation
Grade Aggregate Optimization and Websoc Grades - #546
Open
alexanderl19 wants to merge 3 commits into
Open
alexanderl19 wants to merge 3 commits into
alexanderl19 wants to merge 3 commits into
Conversation
alexanderl19
temporarily deployed
to
staging-546
November 18, 2026 02:18 — with
GitHub Actions
Inactive
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Added materialize views for grade aggregate by course and course / prof pair. These are generated by the grades upload script.
Added the ability to request grade aggregates for course and offerings directly from the WebReg endpoint.
Related Issue
Motivation and Context
AntAlmanac heavily uses these endpoints and shows a use case for requesting these values while listing WebSoc results.
Embedding these values directly into the REST endpoint will reduce the number of request dramatically. Adding the materialized view for the base non filter case improved performance by roughly 22x (pg cpu time measured locally).
How Has This Been Tested?
Tested REST API endpoint locally with db dump. GraphQL optimizations and regression not tested.
Screenshots (if appropriate):
Types of changes
Checklist: